Update mockito monorepo to v5 (major) #18
+2
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.11.0
->5.14.2
4.11.0
->5.14.2
Release Notes
mockito/mockito (org.mockito:mockito-junit-jupiter)
v5.14.2
Changelog generated by Shipkit Changelog Gradle Plugin
5.14.2
mockito-
prefix (#3460)v5.14.1
Changelog generated by Shipkit Changelog Gradle Plugin
5.14.1
v5.14.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.14.0
v5.13.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.13.0
Only.verify
throwsNullPointerException
(#3237)v5.12.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.12.0
AdditionalMatchers.and()
andAdditionalMatchers.or()
not to swap the order of matchers (#3335)v5.11.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.11.0
@Captor
test parameters don't work with primitive type arguments (#3229)v5.10.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.10.0
v5.9.0
What's Changed
New Contributors
Full Changelog: mockito/mockito@v5.8.0...v5.9.0
v5.8.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.8.0
v5.7.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.7.0
0.8.11
(#3147)v5.6.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.6.0
Optional
is notempty
when usingRETURN_DEEP_STUBS
(#2865)v5.5.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.5.0
v5.4.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.4.0
@Mock(serializable = true)
for parameterized types. (#3007)ArgumentMatchers#any()
JavaDoc(#3003)
@Mock(serializable = true)
no longer works with parameterized types (#2979)v5.3.1
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.3.1
v5.3.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.3.0
withoutAnnotations
parameter to@Mock
(#2965)ArgumentMatchers#assertArg
method. (#2949)v5.2.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.2.0
v5.1.1
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.1.1
v5.1.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.1.0
CONTRIBUTING.md
(#2870)CONTRIBUTING.md
(#2868)Mockito#{mock,spy}(T... reified)
with@SafeVarargs
(#2866)v5.0.0
Compare Source
Mockito 5: prepare for future JDK versions
For a while now, we have seen an increase in problems/incompatibilities with recent versions of the JDK due to our usage of JVM-internal API.
Most notably, JDK 17 made some changes which are incompatible with the current subclass mockmaker.
Therefore, to prepare for the future of JDK, we are making some core changes to ensure Mockito keeps on working.
Switch the default mockmaker to
mockito-inline
Back in Mockito 2.7.6, we published a new mockmaker based on the "inline bytecode" principle.
This mockmaker creates mocks manipulating bytecode equivalent within the original class such that its method implementations hook into the normal Mockito machinery.
As a comparison, the subclass mockmaker generates "real" subclasses for mocks, to mimic the same behavior.
While the approaches are similar, the inline mockmaker avoids certain restrictions that the JDK imposes.
For example, it does not violate module boundaries (introduced in JDK 9, but more heavily used in JDK 17) and avoids the leaking of the creation of the subclass.
Massive thanks to community member @reta who implemented this change.
Note: this does not affect
mockito-android
nor testing on Android.When should I still be using the subclass mockmaker?
There are legitimate remaining use cases for the subclass mockmaker.
For example, on the Graal VM's native image, the inline mockmaker will not work and the subclass mockmaker is the appropriate choice.
Additionally, if you would like to avoid mocking final classes, using the subclass mockmaker is a possibibility.
Note however that if you solely want to use the subclass mockmaker to avoid mocking final, you will run into the above mentioned issues on JDK 17+.
We want to leave this choice up to our users, which is why we will keep on supporting the subclass mockmaker.
If you want to use the subclass mockmaker instead, you can use the new
mockito-subclass
artifact (published on Maven Central along with all our other artifacts).Update the minimum supported Java version to 11
Mockito 4 supports Java 8 and above.
Similar to other open source projects, we are moving away from JDK 8 and to newer versions.
The primary reason for moving away from JDK 8 is the increasing maintenance costs with keeping our own infrastructure working.
Lately we have been running into more and more JDK 8 breakages.
Additionally, while we want to support the newest JDK API's, our current solution to support both JDK 8 and newer versions causes issues with the
SecurityManager
.Since we want Mockito to work on the newest version and more and more businesses adopting JDK 11, we have decided to make the switch as well.
Massive thanks to community member [@̴
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.